What can you do with this server?

The cloud-audit MCP server enables AI agents to perform AWS security auditing through six tools: * scan_aws — Scan AWS accounts for misconfigurations across 18+ services, detect attack chains, and estimate breach costs. Supports AWS CLI profile, regions, and severity filters. * get_findings — Retrieve findings from the latest scan, filterable by severity (critical/high/medium/low) and AWS service prefix. Each finding includes check ID, severity, affected resource, description, and estimated breach cost. * get_attack_chains — Fetch correlated findings that form exploitable end-to-end attack paths, each with a narrative, priority fix recommendation, and breach cost estimate. * get_remediation — Get copy-paste ready AWS CLI commands and Terraform HCL snippets to fix a specific security check by ID. * get_health_score — Retrieve a 0–100 security health score with finding counts by severity, attack chain count, and total estimated risk exposure in USD. * list_checks — List all 80 available security checks organized by service/category, no AWS credentials required.

Which integrations are available for this server?

Enables scanning of AWS accounts to detect security vulnerabilities and multi-step attack chains, providing breach cost estimations and remediation guidance via AWS CLI commands and Terraform HCL.

cloud-audit by gebalamariusz

Quick Start

pip install cloud-audit
cloud-audit scan

Uses your default AWS credentials and region. Try without an AWS account:

cloud-audit demo

What You Get

+------- Health Score -------+
| 42 / 100                   |   Risk exposure: $725K - $7.3M
+----------------------------+

+---- Attack Chains (3 detected) -----------------------------------+
|  CRITICAL  Internet-Exposed Admin Instance                         |
|            i-0abc123 - public SG + admin IAM role + IMDSv1         |
|            Fix: Restrict security group (effort: LOW)              |
|                                                                    |
|  CRITICAL  CI/CD to Admin Takeover                                 |
|            github-deploy - OIDC no sub + admin policy              |
|            Fix: Add sub condition (effort: LOW)                    |
+--------------------------------------------------------------------+

Findings by severity:  CRITICAL: 3  HIGH: 8  MEDIUM: 12  LOW: 5

80 checks across 18 AWS services. Every finding includes AWS CLI + Terraform remediation.

If cloud-audit helped you find something you missed, consider giving it a star. It helps others discover the project.

Features

Attack Chain Detection

Other scanners give you a flat list of findings. cloud-audit correlates them into attack paths an attacker would actually exploit.

  Internet --> Public SG --> EC2 (IMDSv1) --> Admin IAM Creds --> Account Takeover
               aws-vpc-002   aws-ec2-004       Detected: AC-01, AC-02

Examples from the 20 built-in rules:

Chain	What it catches
Internet-Exposed Admin Instance	Public SG + admin IAM role + IMDSv1 = account takeover
CI/CD to Admin Takeover	OIDC without sub condition + admin policy = pipeline hijack
SSRF to Credential Theft	Public instance + IMDSv1 + no VPC flow logs = invisible exfiltration

Based on MITRE ATT&CK Cloud and Datadog pathfinding.cloud. See all 20 rules in the docs.

Copy-Paste Remediation

Every finding includes AWS CLI commands, Terraform HCL, and documentation links. Export all fixes as a runnable script:

cloud-audit scan --export-fixes fixes.sh

Scan Diff

Compare scans to track drift. Catches ClickOps changes, manual console edits, and regressions that IaC scanning misses.

cloud-audit diff yesterday.json today.json

Exit code 0 = no new findings, 1 = regression. See daily-scan-with-diff.yml for a CI/CD workflow.

CIS AWS v3.0 Compliance

Built-in compliance engine with per-control evidence, readiness scoring, and auditor-ready reports.

CIS AWS v3.0 - 62 controls, 55 automated (89%)
SOC 2 Type II - 43 criteria, 24 automated (56%)

Planned: BSI C5, ISO 27001, HIPAA, NIS2.

Breach Cost Estimation

Every finding includes a dollar-range risk estimate based on published breach data (IBM Cost of a Data Breach 2024, Verizon DBIR, enforcement actions). Attack chains use compound risk multipliers. Every estimate links to its source.

MCP Server for AI Agents

Ask Claude Code, Cursor, or VS Code Copilot to scan your AWS account:

claude mcp add cloud-audit -- uvx --from cloud-audit cloud-audit-mcp

6 tools: scan_aws, get_findings, get_attack_chains, get_remediation, get_health_score, list_checks. Free and standalone - no SaaS account needed.

How It Compares

Feature	Prowler	Trivy	Checkov	cloud-audit
Checks	576	517	2500+	80
Attack chain detection	No	No	No	20 rules
Remediation per finding	CIS only	No	Links	100% (CLI + Terraform)
Breach cost estimation	No	No	No	Per finding + chain
CIS v3.0 compliance engine	Yes	No	No	62 controls with evidence
SOC 2 Type II compliance	No	No	No	43 criteria with evidence
MCP server (AI agents)	Paid ($99/mo)	No	No	Free, standalone

cloud-audit has fewer checks than Prowler but deeper output per finding: remediation code, attack chain context, cost estimates, and compliance evidence. If you need exhaustive compliance coverage across multiple clouds, Prowler is the better choice. If you need a focused scan that shows how findings combine into real attack paths and tells you exactly how to fix each one, cloud-audit is built for that.

Feature snapshot as of March 2026. Verify against upstream docs for the latest details.

Reports

cloud-audit scan --format html --output report.html    # Client-ready HTML
cloud-audit scan --format json --output report.json    # Machine-readable
cloud-audit scan --format sarif --output results.sarif # GitHub Code Scanning
cloud-audit scan --format markdown --output report.md  # PR comments

Format is auto-detected from file extension.

Installation

pip install cloud-audit          # pip (recommended)
pipx install cloud-audit         # pipx (isolated)
docker run ghcr.io/gebalamariusz/cloud-audit scan  # Docker

Docker with credentials:

docker run -v ~/.aws:/home/cloudaudit/.aws:ro ghcr.io/gebalamariusz/cloud-audit scan

Usage

cloud-audit scan -R                                    # Show remediation
cloud-audit scan --profile prod --regions eu-central-1  # Specific profile/region
cloud-audit scan --regions all                          # All enabled regions
cloud-audit scan --min-severity high                   # Filter by severity
cloud-audit scan --role-arn arn:aws:iam::...:role/audit # Cross-account
cloud-audit scan --quiet                               # Exit code only (CI/CD)
cloud-audit list-checks                                # List all checks

Exit code	Meaning
0	No findings
1	Findings detected
2	Scan error

Create .cloud-audit.yml in your project root:

provider: aws
regions:
  - eu-central-1
  - eu-west-1
min_severity: medium
exclude_checks:
  - aws-eip-001
suppressions:
  - check_id: aws-vpc-001
    resource_id: vpc-abc123
    reason: "Legacy VPC, migration planned for Q3"
    accepted_by: "jane@example.com"
    expires: "2026-09-30"
  - check_id: "aws-cw-*"
    reason: "CloudWatch alarms managed by separate team"
    accepted_by: "ops@example.com"

Variable	Example
`CLOUD_AUDIT_REGIONS`	`eu-central-1,eu-west-1`
`CLOUD_AUDIT_MIN_SEVERITY`	`high`
`CLOUD_AUDIT_EXCLUDE_CHECKS`	`aws-eip-001,aws-iam-001`
`CLOUD_AUDIT_ROLE_ARN`	`arn:aws:iam::...:role/auditor`

Precedence: CLI flags > env vars > config file > defaults.

CI/CD

- run: pip install cloud-audit
- run: cloud-audit scan --format sarif --output results.sarif
- uses: github/codeql-action/upload-sarif@v3
  with:
    sarif_file: results.sarif

Ready-to-use workflows: basic scan, daily diff, post-deploy.

AWS Permissions

cloud-audit requires read-only access. Attach SecurityAudit:

aws iam attach-role-policy --role-name auditor --policy-arn arn:aws:iam::aws:policy/SecurityAudit

cloud-audit never modifies your infrastructure.

What It Checks

80 checks across IAM, S3, EC2, VPC, RDS, EIP, EFS, CloudTrail, GuardDuty, KMS, CloudWatch, Lambda, ECS, SSM, Secrets Manager, AWS Config, Security Hub, and Account.

IAM (16 checks)

ID	Severity	Description
`aws-iam-001`	Critical	Root account without MFA
`aws-iam-002`	High	IAM user with console access but no MFA
`aws-iam-003`	Medium	Access key older than 90 days
`aws-iam-004`	Medium	Access key unused for 45+ days
`aws-iam-005`	Critical	IAM policy with Action:* and Resource:*
`aws-iam-006`	Medium	Password policy below CIS requirements
`aws-iam-007`	Critical	OIDC trust policy without sub condition
`aws-iam-008`	Critical	Root account has active access keys
`aws-iam-009`	Medium	Multiple active access keys per user
`aws-iam-010`	Medium	Direct policy attachment on user (not via group)
`aws-iam-011`	Medium	No AWSSupportAccess role
`aws-iam-012`	Medium	IAM Access Analyzer not enabled
`aws-iam-013`	Medium	Expired SSL/TLS certificate in IAM
`aws-iam-014`	Medium	AWSCloudShellFullAccess attached
`aws-iam-015`	Medium	Root uses virtual MFA (not hardware)
`aws-iam-016`	Medium	EC2 instance without IAM role

S3 (7 checks)

ID	Severity	Description
`aws-s3-001`	High	S3 bucket without public access block
`aws-s3-002`	Low	S3 bucket using SSE-S3 instead of SSE-KMS
`aws-s3-003`	Low	S3 bucket without versioning
`aws-s3-004`	Low	S3 bucket without lifecycle rules
`aws-s3-005`	Medium	S3 bucket without access logging
`aws-s3-006`	Medium	S3 bucket policy does not deny HTTP
`aws-s3-007`	Low	S3 bucket without MFA Delete

EC2 (6 checks)

ID	Severity	Description
`aws-ec2-001`	High	Publicly shared AMI
`aws-ec2-002`	Medium	Unencrypted EBS volume
`aws-ec2-003`	Low	Stopped EC2 instance (EBS charges continue)
`aws-ec2-004`	High	EC2 instance with IMDSv1 (SSRF risk)
`aws-ec2-005`	Low	EC2 instance without termination protection
`aws-ec2-006`	Medium	EBS default encryption disabled

VPC (5 checks)

ID	Severity	Description
`aws-vpc-001`	Medium	Default VPC in use
`aws-vpc-002`	Critical	Security group open to 0.0.0.0/0 or ::/0 on sensitive ports
`aws-vpc-003`	Medium	VPC without flow logs
`aws-vpc-004`	Medium	NACL allows internet access to admin ports
`aws-vpc-005`	Medium	Default security group has active rules

RDS (4 checks)

ID	Severity	Description
`aws-rds-001`	Critical	Publicly accessible RDS instance
`aws-rds-002`	High	Unencrypted RDS instance
`aws-rds-003`	Medium	Single-AZ RDS instance
`aws-rds-004`	Low	RDS auto minor version upgrade disabled

CloudTrail (7 checks)

ID	Severity	Description
`aws-ct-001`	Critical	No multi-region CloudTrail trail
`aws-ct-002`	High	CloudTrail log file validation disabled
`aws-ct-003`	Critical	CloudTrail S3 bucket is publicly accessible
`aws-ct-004`	High	CloudTrail S3 bucket has no access logging
`aws-ct-005`	Medium	CloudTrail not encrypted with KMS
`aws-ct-006`	Medium	S3 object-level write events not logged
`aws-ct-007`	Medium	S3 object-level read events not logged

CloudWatch (15 checks)

ID	Severity	Description
`aws-cw-001`	High	No alarm for root account usage
`aws-cw-002`	Medium	No alarm for unauthorized API calls
`aws-cw-003`	Medium	No alarm for console sign-in without MFA
`aws-cw-004`	Medium	No alarm for IAM policy changes
`aws-cw-005`	Medium	No alarm for CloudTrail config changes
`aws-cw-006`	Medium	No alarm for console auth failures
`aws-cw-007`	Medium	No alarm for CMK disable/deletion
`aws-cw-008`	Medium	No alarm for S3 bucket policy changes
`aws-cw-009`	Medium	No alarm for Config changes
`aws-cw-010`	Medium	No alarm for security group changes
`aws-cw-011`	Medium	No alarm for NACL changes
`aws-cw-012`	Medium	No alarm for network gateway changes
`aws-cw-013`	Medium	No alarm for route table changes
`aws-cw-014`	Medium	No alarm for VPC changes
`aws-cw-015`	Medium	No alarm for Organizations changes

Other Services (20 checks)

ID	Severity	Description
`aws-gd-001`	High	GuardDuty not enabled
`aws-gd-002`	Medium	GuardDuty findings unresolved for 30+ days
`aws-cfg-001`	Medium	AWS Config not enabled
`aws-cfg-002`	High	AWS Config recorder stopped
`aws-kms-001`	Medium	KMS key without automatic rotation
`aws-kms-002`	High	KMS key policy with Principal:*
`aws-lambda-001`	High	Lambda function URL with no authentication
`aws-lambda-002`	Medium	Lambda running on a deprecated runtime
`aws-lambda-003`	High	Potential secrets in Lambda env vars
`aws-ecs-001`	Critical	ECS task running in privileged mode
`aws-ecs-002`	High	ECS task without log configuration
`aws-ecs-003`	Medium	ECS service with Execute Command enabled
`aws-ssm-001`	Medium	EC2 instance not managed by SSM
`aws-ssm-002`	High	SSM parameter stored as plain String
`aws-sm-001`	Medium	Secret without rotation
`aws-sm-002`	Low	Secret unused for 90+ days
`aws-eip-001`	Low	Unattached Elastic IP
`aws-efs-001`	Medium	EFS file system not encrypted
`aws-sh-001`	Medium	Security Hub not enabled
`aws-account-001`	Medium	No security alternate contact

Alternatives

Prowler - 576+ checks, multi-cloud, full CIS coverage, auto-remediation. The most comprehensive open-source scanner.
Trivy - Container, IaC, and cloud scanner. Strong on containers, growing cloud coverage.
Steampipe - SQL-based cloud querying. Very flexible.
AWS Security Hub - Native AWS service with continuous monitoring. Free 30-day trial.

Documentation

cloud-audit has grown beyond what a single README can cover. The full documentation is at haitmg.pl/cloud-audit and includes:

Getting Started - installation, quick start, demo mode
Compliance - CIS AWS v3.0 with all 62 controls, planned SOC 2, BSI C5, HIPAA, NIS2
Attack Chains - all 20 rules with MITRE ATT&CK references
MCP Server - full setup guide for Claude Code, Cursor, VS Code
Configuration - config file, env vars, suppressions
CI/CD - GitHub Actions, SARIF, pre-commit hooks
Reports - HTML, JSON, SARIF, Markdown output formats
All 80 Checks - full check reference by service

This README covers the essentials. For compliance framework details, advanced configuration, and per-check documentation, see the full docs.

What's Next

SOC 2, BSI C5, HIPAA, NIS2 compliance frameworks
Terraform drift detection
Root cause grouping

Past releases: CHANGELOG.md

Development

git clone https://github.com/gebalamariusz/cloud-audit.git
cd cloud-audit
pip install -e ".[dev]"

pytest -v                          # tests
ruff check src/ tests/             # lint
ruff format --check src/ tests/    # format
mypy src/                          # type check

See CONTRIBUTING.md for how to add a new check.

License

MIT - Mariusz Gebala / HAIT

cloud-audit